⬆️ #10: Upgrade Dependency jasmine-core to v5 #20

/usr/local/bin/docker: line 4: .: filename argument required
.: usage: . filename [arguments]
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/jasmine-core
npm ERR!   dev jasmine-core@"~5.1.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer jasmine-core@"^4.0.0" from [email protected]
npm ERR! node_modules/karma-jasmine-html-reporter
npm ERR!   dev karma-jasmine-html-reporter@"~2.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/jasmine-core
npm ERR!   peer jasmine-core@"^4.0.0" from [email protected]
npm ERR!   node_modules/karma-jasmine-html-reporter
npm ERR!     dev karma-jasmine-html-reporter@"~2.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/eb49aa/3b8ef6/cache/others/npm/_logs/2023-07-23T05_19_55_456Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/eb49aa/3b8ef6/cache/others/npm/_logs/2023-07-23T05_19_55_456Z-debug-0.log

sonarqubecloud · 2023-07-27T17:51:55Z

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

renovate · 2024-07-21T17:53:19Z

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/jasmine-core
npm error   dev jasmine-core@"~5.12.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer jasmine-core@"^4.0.0" from [email protected]
npm error node_modules/karma-jasmine-html-reporter
npm error   dev karma-jasmine-html-reporter@"~2.0.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/jasmine-core
npm error   peer jasmine-core@"^4.0.0" from [email protected]
npm error   node_modules/karma-jasmine-html-reporter
npm error     dev karma-jasmine-html-reporter@"~2.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-11-01T12_05_59_377Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-11-01T12_05_59_377Z-debug-0.log